Nectar Logo

User-Centred Requirements Handbook

Telematics Engineering Logo

Phase 3. User requirements documentation


3.5 System functions and features

Objective

This section lists the system functions and features that have arisen during the analysis and concept stages and by considering new tasks.

Process

1. Review all the potential user requirements identified in Stages 1 and 2, particularly in:

• Form 1.8 Review current processes

• Form 1.9 Review other systems and products

• Form 1.10 Design ideas and concepts

Form 2.4 Propose new processes

Copy those that relate to system functions and into Form 3.5.1 below, and those that relate to system features and into Form 3.5.2.

2. Remove any requirements that duplicate others or do not seem relevant.

3. Add any new requirements which arise from the review of this section.

To perform a check of the system functions and features, a functionality matrix (section 4.5) can be used. This is essentially a matrix which matches proposed system functions across all user tasks. It provides a check as to whether any additional functions are required to support some tasks or whether any functions should be removed or amalgamated because they support the same tasks. The matrix can also act as documentation to demonstrate the need for all the functions included within the system.

Form 3.5.1 - System Functions (Example)

3.5.1 System Functions

System: New bank machine
Transfer from Form 1.8 Review current processes
Form 1.9 Review other systems and products
Form 1.10 Design ideas and concepts
and Form 2.4 Propose new processes

Pri.

1-5


Ach.
*
**
***

Ref.



Provide security feature e.g. alarm button. 3 * 1.3.17
Bank machine could be adapted to automatically send a message to maintenance if a major failure occurs. 4 ** 1.4.5
If user forgets PIN, system returns card for user to take into bank. If card not shown to bank within 5 days, it is cancelled and letter sent to customer with new card. 4   2.6.1
Allow PIN or thumbprint for verification. 4  
1.8.3
2.4.4
If machine abandoned, provide quick reset button 4 ** 1.8.4
Low warning before machine runs out of money 2 *** 1.9.3
Low warning before machine runs out of paper 3 *** 1.9.4
Allow user to notify bank if card gets stuck in the machine, by pressing special button - Good idea as long as button only active for when card is actually lost in the machine 3   1.11.3
System displays maximum amount that can be withdrawn. 2 *** 2.4.5

Form 3.5.2 - System Features (Example)

3.5.2 System Features

System: New bank machine
Transfer from Form 1.8 Review current processes
Form 1.9 Review other systems and products
Form 1.10 Design ideas and concept
and Form 2.4 Propose new processes
Pri. Ach. Ref.
Use English language and up to 8 other language options, depending on local area. 4 * 1.3.3
Use highly supportive interface with clear logical structure and which are easy to learn and remember 2 **
1.3.11
1.3.13
Use terms that the user will understand 2 *** 1.3.12
Ensure design allows privacy when using machine. 2 * 1.3.18
To assist user in orienting card properly provide notch on card and and picture on machine as guidance
3

3

***

***

1.8.1
1.8.2
2.4.2
Display amount available that can be withdrawn from the account. 2 *** 1.8.6
Provide cancel button if user decides not proceed with transaction. 4   1.8.7
Provide short cuts to commonly required options. 3 * 1.8.8
If user does not receive expected money or no receipt returned, provide button to register problem at given time. Allow them to report the fault by video camera. 3 *
1.8.9
2.6.2
Provide camera on bank machine to record possible threatening behaviour to user by passers-by 4   1.8.10
Question and Answer mode for beginners - Useful idea but may slow down the interaction process 4 * 1.11.2
Develop reader that will read card whichever way it is inserted. 3 ** 2.4.1
System offers options: 'Withdraw £20, £50, £100' on first menu. 3 *** 2.4.6
Allow user to select : 'Cash with receipt' or 'Cash without receipt' 2 *** 2.4.7
Machine gives out of service notice before next card inserted. 2 **  
Exit button provided. 3 *  
Fast path available giving standard amount of money 4    
User asked if happy to continue withdrawing cash without receipt. 3 **  
Help button which user can press to register problem. Reference number displayed which can be quoted inside bank. 3    
Develop faster refill mechanism. 2 ** 2.7.2

3.6 User interface design
Back to Contents

NECTAR Home Page The NECTAR Information Update The NECTAR Repository The European Journal of Engineering for Information Society Applications The NECTAR Discussion Fora